Micron Document
<!DOCTYPE html>
<html class="client-nojs vector-feature-night-mode-disabled vector-feature-language-in-header-enabled vector-feature-language-in-main-page-header-disabled vector-feature-page-tools-pinned-disabled vector-feature-toc-pinned-clientpref-1 vector-feature-main-menu-pinned-disabled vector-feature-limited-width-clientpref-1 vector-feature-limited-width-content-enabled vector-feature-custom-font-size-clientpref-1 vector-feature-appearance-pinned-clientpref-1 vector-sticky-header-enabled" lang="en" dir="ltr"><head>
<meta charset="UTF-8">
<title>Time-utility function</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
<link rel="canonical" href="https://en.wikipedia.org/wiki/Time-utility_function"> <link href="./mw/ext.cite.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.icons.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.search.codex.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/skins.vector.styles.css" rel="stylesheet" type="text/css">
<link href="./mw/user.styles.css" rel="stylesheet" type="text/css">
<meta name="ResourceLoaderDynamicStyles" content="">
<link rel="stylesheet" type="text/css" href="./mw/site.styles.css">
<link rel="stylesheet" type="text/css" href="./mw/noscript.css">
<link rel="stylesheet" type="text/css" href="./footer.css">
<link rel="stylesheet" type="text/css" href="./vector-2022.css">
</head>
<body class="skin--responsive skin-vector skin-vector-search-vue mediawiki ltr sitedir-ltr mw-hide-empty-elt ns-0 ns-subject page-Time-utility_function rootpage-Time-utility_function skin-vector-2022 action-view">
<div class="mw-page-container">
<div class="mw-page-container-inner">
<div class="mw-content-container">
<main id="content" class="mw-body">
<header class="mw-body-header vector-page-titlebar">
<h1 id="firstHeading" class="firstHeading mw-first-heading">
<span id="openzim-page-title" class="mw-page-title-main"><span class="mw-page-title-main">Time-utility function</span></span>
</h1>
</header>
<a id="top"></a>
<div id="bodyContent" class="vector-body ve-init-mw-desktopArticleTarget-targetContainer" aria-labelledby="firstHeading" data-mw-ve-target-container="">
<div id="mw-content-text" class="mw-body-content mw-content-ltr" lang="en" dir="ltr"><div class="mw-content-ltr mw-parser-output" lang="en" dir="ltr"><p>A <b>Time/Utility Function</b> (<i>TUF</i>), née <i>Time/Value Function</i>, specifies the application-specific <i>utility</i> that an <i>action</i> (e.g., computational task, mechanical movement) yields depending on its completion time.<sup id="cite_ref-Jensen+_85_1-0" class="reference"><a href="#cite_note-Jensen+_85-1"><span class="cite-bracket">[</span>1<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Jensen_93_2-0" class="reference"><a href="#cite_note-Jensen_93-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> TUFs and their utility interpretations (semantics), scales, and values are derived from application domain-specific subject matter knowledge. An example (but not the only) interpretation of utility is an action's relative <i>importance,</i> which otherwise is independent of its <i>timeliness</i>. The traditional deadline represented as a TUF is a special case—a downward step of utility from 1 to 0 at the deadline time—e.g., timeliness without importance. A TUF is more general—it has a <i>critical time,</i> with application-specific shapes and utility values on each side, after which it does not increase. The various researcher and practitioner definitions of <i>firm</i> and <i>soft</i> real-time can also be represented as special cases of the TUF model. </p>
<p>The optimality criterion for <a href="Scheduling" class="mw-redirect" title="Scheduling">scheduling</a> multiple TUF-constrained actions has historically in the literature been only maximal <i>utility accrual</i> (<i>UA</i>)—e.g., a (perhaps expected) weighted sum of the individual actions' completion utilities. This thus takes into account timeliness with respect to critical times. Additional criteria (e.g., energy, predictability), constraints (e.g., dependencies), system models, scheduling algorithms, and assurances have been added as the TUF/UA paradigm and its use cases have evolved. More expressively, TUF/UA allows accrued utility, timeliness, predictability, and other scheduling criteria and constraints to be traded off against one another for the schedule to yield situational <i>application QoS</i><sup id="cite_ref-3" class="reference"><a href="#cite_note-3"><span class="cite-bracket">[</span>a<span class="cite-bracket">]</span></a></sup>—as opposed to only timeliness per se. Instances of the TUF/UA paradigm have been employed in a wide variety of application domains, most frequently in military systems.
</p>
<meta property="mw:PageProp/toc">
<div class="mw-heading mw-heading2"><h2 id="Time/Utility_Functions">Time/Utility Functions</h2></div>
<p>The TUF/UA paradigm was originally created to address certain action timeliness, predictability of timeliness, and <i>application QoS</i>-based scheduling needs of various military applications for which traditional real-time concepts and practices are not sufficiently expressive (e.g., for dynamically timeliness-critical systems not having deadlines) and load resilience (e.g., for systems subject to routine action overloads). An important common example class of such applications is missile defense (notionally<sup id="cite_ref-Jensen_77_4-0" class="reference"><a href="#cite_note-Jensen_77-4"><span class="cite-bracket">[</span>3<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Gouda+_77_5-0" class="reference"><a href="#cite_note-Gouda+_77-5"><span class="cite-bracket">[</span>4<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Maynard+_88_&amp;_08_6-0" class="reference"><a href="#cite_note-Maynard+_88_&amp;_08-6"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>).
</p><p>Subsequently, numerous variations on the original TUF model, the TUF/UA paradigm's system model, and thus scheduling techniques and algorithms, have been studied in the academic literature—e.g.,<sup id="cite_ref-Ravindran+_05_7-0" class="reference"><a href="#cite_note-Ravindran+_05-7"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Aldami+_99_8-0" class="reference"><a href="#cite_note-Aldami+_99-8"><span class="cite-bracket">[</span>7<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Burns+_00_9-0" class="reference"><a href="#cite_note-Burns+_00-9"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Prasad+_03_10-0" class="reference"><a href="#cite_note-Prasad+_03-10"><span class="cite-bracket">[</span>9<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Chen+_96_11-0" class="reference"><a href="#cite_note-Chen+_96-11"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup>—and applied in civilian contexts.
</p><p>
Some examples of the latter include: cyber-physical systems,<sup id="cite_ref-Tidwell+_10_12-0" class="reference"><a href="#cite_note-Tidwell+_10-12"><span class="cite-bracket">[</span>11<span class="cite-bracket">]</span></a></sup> AI,<sup id="cite_ref-Ronén+_99_13-0" class="reference"><a href="#cite_note-Ronén+_99-13"><span class="cite-bracket">[</span>12<span class="cite-bracket">]</span></a></sup> multi-robot systems,<sup id="cite_ref-Barcís_20_14-0" class="reference"><a href="#cite_note-Barcís_20-14"><span class="cite-bracket">[</span>13<span class="cite-bracket">]</span></a></sup> drone scheduling,<sup id="cite_ref-Shireen_Seakhoa-King+_19_15-0" class="reference"><a href="#cite_note-Shireen_Seakhoa-King+_19-15"><span class="cite-bracket">[</span>14<span class="cite-bracket">]</span></a></sup> autonomous robots,<sup id="cite_ref-Baums_12_16-0" class="reference"><a href="#cite_note-Baums_12-16"><span class="cite-bracket">[</span>15<span class="cite-bracket">]</span></a></sup> intelligent vehicle-to-cloud data transfers,<sup id="cite_ref-Ibarz+_20_17-0" class="reference"><a href="#cite_note-Ibarz+_20-17"><span class="cite-bracket">[</span>16<span class="cite-bracket">]</span></a></sup> industrial process control,<sup id="cite_ref-Habets_19_18-0" class="reference"><a href="#cite_note-Habets_19-18"><span class="cite-bracket">[</span>17<span class="cite-bracket">]</span></a></sup> transaction systems,<sup id="cite_ref-Haritsa+_93_19-0" class="reference"><a href="#cite_note-Haritsa+_93-19"><span class="cite-bracket">[</span>18<span class="cite-bracket">]</span></a></sup> high performance computing,<sup id="cite_ref-Briceño+_11_20-0" class="reference"><a href="#cite_note-Briceño+_11-20"><span class="cite-bracket">[</span>19<span class="cite-bracket">]</span></a></sup> cloud systems,<sup id="cite_ref-Tunc+_16_21-0" class="reference"><a href="#cite_note-Tunc+_16-21"><span class="cite-bracket">[</span>20<span class="cite-bracket">]</span></a></sup> heterogeneous clusters,<sup id="cite_ref-Ravi+_12_22-0" class="reference"><a href="#cite_note-Ravi+_12-22"><span class="cite-bracket">[</span>21<span class="cite-bracket">]</span></a></sup> service-oriented computing,<sup id="cite_ref-Young+_06_23-0" class="reference"><a href="#cite_note-Young+_06-23"><span class="cite-bracket">[</span>22<span class="cite-bracket">]</span></a></sup> networking,<sup id="cite_ref-Wang+_04_24-0" class="reference"><a href="#cite_note-Wang+_04-24"><span class="cite-bracket">[</span>23<span class="cite-bracket">]</span></a></sup> and memory management for real<sup id="cite_ref-Cho+_09_25-0" class="reference"><a href="#cite_note-Cho+_09-25"><span class="cite-bracket">[</span>24<span class="cite-bracket">]</span></a></sup> and virtual<sup id="cite_ref-Feizabadi+_07_26-0" class="reference"><a href="#cite_note-Feizabadi+_07-26"><span class="cite-bracket">[</span>25<span class="cite-bracket">]</span></a></sup> machines. A steel mill example is briefly described in the Introduction of Clark's Ph.D. thesis.<sup id="cite_ref-Clark_90_27-0" class="reference"><a href="#cite_note-Clark_90-27"><span class="cite-bracket">[</span>26<span class="cite-bracket">]</span></a></sup>
</p><p>TUFs and their utility interpretations (semantics), scales, and values are derived from domain-specific subject matter knowledge.<sup id="cite_ref-Clark+_99_28-0" class="reference"><a href="#cite_note-Clark+_99-28"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Maynard+_88_&amp;_08_6-1" class="reference"><a href="#cite_note-Maynard+_88_&amp;_08-6"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup> A historically frequent interpretation of utility is actions' relative <i>importance.</i><sup id="cite_ref-29" class="reference"><a href="#cite_note-29"><span class="cite-bracket">[</span>b<span class="cite-bracket">]</span></a></sup> A framework for á priori assigning static utility values subject to strong constraints on system models has been devised,<sup id="cite_ref-Burns+_00_9-1" class="reference"><a href="#cite_note-Burns+_00-9"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup> but subsequent (like prior) TUF/UA research and development have preferred to depend on exploiting application-specificity rather than attempting to create more general frameworks. However, such frameworks and tools remain an important research topic.
</p><p>By traditional convention, a TUF is a <a href="Concave_function" title="Concave function">concave function</a>, including linear ones. See the depiction of some example TUFs.
</p><p>TUF/UA papers in the research literature, with few exceptions, e.g.,<sup id="cite_ref-Locke_86_30-0" class="reference"><a href="#cite_note-Locke_86-30"><span class="cite-bracket">[</span>28<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Ravindran+_05_7-1" class="reference"><a href="#cite_note-Ravindran+_05-7"><span class="cite-bracket">[</span>6<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Li_04_31-0" class="reference"><a href="#cite_note-Li_04-31"><span class="cite-bracket">[</span>29<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Li+_06_32-0" class="reference"><a href="#cite_note-Li+_06-32"><span class="cite-bracket">[</span>30<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Burns+_00_9-2" class="reference"><a href="#cite_note-Burns+_00-9"><span class="cite-bracket">[</span>8<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Chen+_96_11-1" class="reference"><a href="#cite_note-Chen+_96-11"><span class="cite-bracket">[</span>10<span class="cite-bracket">]</span></a></sup> are for only either linear or piecewise linear<sup id="cite_ref-Guo+_16_33-0" class="reference"><a href="#cite_note-Guo+_16-33"><span class="cite-bracket">[</span>31<span class="cite-bracket">]</span></a></sup> (including conventional deadline-based) TUFs because they are easier to specify and schedule. In many cases, the TUFs are only <a class="external text external" href="https://en.wiktionary.org/wiki/monotonic_decreasing#:~:text=English-,Adjective,contrast%20this%20with%20strictly%20decreasing">monotonically decreasing</a>.
</p><p>A <a href="Constant_function" title="Constant function">constant function</a> represents an action's utility that is not related to the action's completion time—for example, the action's constant relative importance. This allows both time-dependent and time-independent actions to be scheduled coherently.
</p><p>A TUF has a global <i>critical time</i>, after which its utility does not increase. If a TUF never decreases, its global critical time is the first time when its maximum utility is reached. A constant TUF has an arbitrary critical time for the purpose of scheduling—such as the action's release time, or the TUF's termination time. The global critical time may be followed by local critical times<sup id="cite_ref-Jensen_93_2-1" class="reference"><a href="#cite_note-Jensen_93-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup>—for example, consider a TUF having a sequence of downward steps, perhaps to approximate a smooth downward curve.<sup id="cite_ref-34" class="reference"><a href="#cite_note-34"><span class="cite-bracket">[</span>c<span class="cite-bracket">]</span></a></sup>
</p><p>TUF utility values are usually either integers or rational numbers.
</p><p>TUF utility may include negative values. (A TUF that has negative values in its range is not necessarily dropped from scheduling consideration or aborted during its operation—that decision depends on the scheduling algorithm.)
</p><p>A conventional deadline time (<i><b>d</b></i>) represented as a TUF is a special case—a downward step TUF<sup id="cite_ref-35" class="reference"><a href="#cite_note-35"><span class="cite-bracket">[</span>d<span class="cite-bracket">]</span></a></sup> having a unit penalty (i.e., having utility values <i>1</i> before and <i>0</i> after its critical time).
</p><p>More generally, a TUF allows downward (and upward) step functions to have any pre- and post-critical time utilities.
</p><p><a href="Tardiness" title="Tardiness">Tardiness</a><sup id="cite_ref-Erikson_14_36-0" class="reference"><a href="#cite_note-Erikson_14-36"><span class="cite-bracket">[</span>32<span class="cite-bracket">]</span></a></sup> represented as a TUF is a special case whose non-zero utility is the <i>linear</i> function <i><b>C</b> - <b>d</b></i>, where <i><b>C</b></i> is the action's completion time—either current, expected, or believed.<sup id="cite_ref-37" class="reference"><a href="#cite_note-37"><span class="cite-bracket">[</span>e<span class="cite-bracket">]</span></a></sup> More generally, a TUF allows non-zero earliness and tardiness to be <i>non-linear</i>—e.g., increasing tardiness may result in non-linearly decreasing utility, such as when detecting a threat.
</p><p>Thus, TUFs provide a rich generalization of traditional action completion time constraints in <a href="Real-time_computing" title="Real-time computing">real-time computing</a>.
</p><p>Alternatively, the TUF/UA paradigm can be employed to use timeliness with respect to the global critical time as a means to a utility accrual end—i.e., application-level Quality of Service (QoS)—instead of timeliness per se being an end in itself <style data-mw-deduplicate="TemplateStyles:r1033199720">
/* start https://en.wikipedia.org/ */


.mw-parser-output div.crossreference{padding-left:0}


/* end https://en.wikipedia.org/ */
</style><style data-mw-deduplicate="TemplateStyles:r1236090951">
/* start https://en.wikipedia.org/ */


.mw-parser-output .hatnote{font-style:italic}.mw-parser-output div.hatnote{padding-left:1.6em;margin-bottom:0.5em}.mw-parser-output .hatnote i{font-style:normal}.mw-parser-output .hatnote+link+.hatnote{margin-top:-0.5em}@media print{body.ns-0 .mw-parser-output .hatnote{display:none!important}}


/* end https://en.wikipedia.org/ */
</style><span role="note" class="hatnote navigation-not-searchable crossreference selfref">(see <a href="#Utility_Accrual_Scheduling">below</a>)</span>.
</p><p>A TUF (its shape and values) may be dynamically adapted by an application or its operational environment,<sup id="cite_ref-Jensen_93_2-2" class="reference"><a href="#cite_note-Jensen_93-2"><span class="cite-bracket">[</span>2<span class="cite-bracket">]</span></a></sup> independently for any actions currently either waiting or operating.<sup id="cite_ref-38" class="reference"><a href="#cite_note-38"><span class="cite-bracket">[</span>f<span class="cite-bracket">]</span></a></sup>
</p><p>These adaptations ordinarily occur at discrete events—e.g., at an application mode change such as for ballistic missile flight phases.<sup id="cite_ref-Maynard+_88_&amp;_08_6-2" class="reference"><a href="#cite_note-Maynard+_88_&amp;_08-6"><span class="cite-bracket">[</span>5<span class="cite-bracket">]</span></a></sup>
</p><p>Alternatively, these adaptations may occur continuously, such as for actions whose operational durations and TUFs are application-specific functions of when those actions are either released or begin operation. The operation durations may increase or decrease or both, and may be non-monotonic. This continuous case is called <i>time-dependent scheduling</i>.<sup id="cite_ref-Gawiejnowicz_20a_39-0" class="reference"><a href="#cite_note-Gawiejnowicz_20a-39"><span class="cite-bracket">[</span>33<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Glazebrook_92_40-0" class="reference"><a href="#cite_note-Glazebrook_92-40"><span class="cite-bracket">[</span>34<span class="cite-bracket">]</span></a></sup> Time-dependent scheduling was introduced for (but is not limited to) certain real-time military applications, such as radar tracking systems.<sup id="cite_ref-Balli+_07_41-0" class="reference"><a href="#cite_note-Balli+_07-41"><span class="cite-bracket">[</span>35<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Ho+_93_42-0" class="reference"><a href="#cite_note-Ho+_93-42"><span class="cite-bracket">[</span>36<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-43" class="reference"><a href="#cite_note-43"><span class="cite-bracket">[</span>g<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="Utility_Accrual_Scheduling">Utility Accrual Scheduling</h2></div>
<p>Multiple actions in a system may contend for access to sequentially exclusively<sup id="cite_ref-44" class="reference"><a href="#cite_note-44"><span class="cite-bracket">[</span>h<span class="cite-bracket">]</span></a></sup> shared resources—physical ones such as processors, networks, exogenous application devices (sensors, actuators, etc.)—and logical ones such as synchronizers, data.
</p><p>The TUF/UA paradigm resolves each instance of this contention using an application-specific algorithmic technique that creates (or updates) a <i>schedule</i> at <i>scheduling events</i>—e.g., times (such as action arrival or completion) or states. The instance's contending actions are dispatched for resource access sequentially in order from the front of the schedule. Thus, action UA sequencing is not greedy.<sup id="cite_ref-45" class="reference"><a href="#cite_note-45"><span class="cite-bracket">[</span>i<span class="cite-bracket">]</span></a></sup>
</p><p>The algorithmic technique creates a schedule based on one or more application-specific <i>objectives</i> (i.e., optimality criteria).
</p><p>The primary objective for scheduling actions having TUFs is maximal <i>utility accrual</i> (<i>UA</i>). The accrued utility is an application-specific polynomial sum of the schedule's completed actions' utilities. When actions have one or more stochastic parameters (e.g., operation duration), the accrued utility is also stochastic (i.e., an expected polynomial sum).
</p><p>Utility and accrued utility are generic, their interpretations (semantics) and scales are application-specific.<sup id="cite_ref-Clark+_99_28-1" class="reference"><a href="#cite_note-Clark+_99-28"><span class="cite-bracket">[</span>27<span class="cite-bracket">]</span></a></sup>
</p><p>An action's operation duration may be fixed and known at system configuration time. More generally, it may be either fixed or stochastic but not known (either with certainty or in expectation) until it either arrives or is released.
</p><p>An operation duration may be an application-specific function of the action's operation starting time—it may increase or decrease or both, and may be non-monotonic. This case is called <i>time-dependent scheduling</i>.<sup id="cite_ref-Gawiejnowicz_20a_39-1" class="reference"><a href="#cite_note-Gawiejnowicz_20a-39"><span class="cite-bracket">[</span>33<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Glazebrook_92_40-1" class="reference"><a href="#cite_note-Glazebrook_92-40"><span class="cite-bracket">[</span>34<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Balli+_07_41-1" class="reference"><a href="#cite_note-Balli+_07-41"><span class="cite-bracket">[</span>35<span class="cite-bracket">]</span></a></sup><sup id="cite_ref-Ho+_93_42-1" class="reference"><a href="#cite_note-Ho+_93-42"><span class="cite-bracket">[</span>36<span class="cite-bracket">]</span></a></sup>
</p>
<div class="mw-heading mw-heading2"><h2 id="Notes">Notes</h2></div>
<style data-mw-deduplicate="TemplateStyles:r1239543626">
/* start https://en.wikipedia.org/ */


.mw-parser-output .reflist{margin-bottom:0.5em;list-style-type:decimal}@media screen{.mw-parser-output .reflist{font-size:90%}}.mw-parser-output .reflist .references{font-size:100%;margin-bottom:0;list-style-type:inherit}.mw-parser-output .reflist-columns-2{column-width:30em}.mw-parser-output .reflist-columns-3{column-width:25em}.mw-parser-output .reflist-columns{margin-top:0.3em}.mw-parser-output .reflist-columns ol{margin-top:0}.mw-parser-output .reflist-columns li{page-break-inside:avoid;break-inside:avoid-column}.mw-parser-output .reflist-upper-alpha{list-style-type:upper-alpha}.mw-parser-output .reflist-upper-roman{list-style-type:upper-roman}.mw-parser-output .reflist-lower-alpha{list-style-type:lower-alpha}.mw-parser-output .reflist-lower-greek{list-style-type:lower-greek}.mw-parser-output .reflist-lower-roman{list-style-type:lower-roman}


/* end https://en.wikipedia.org/ */
</style><div class="reflist reflist-lower-alpha">
<div class="mw-references-wrap"><ol class="references">
<li id="cite_note-3"><span class="mw-cite-backlink"><b><a href="#cite_ref-3">^</a></b></span> <span class="reference-text">The term <i>Quality of Service (QoS)</i> initially arose in the context of communication networks but subsequently has commonly been applied at the application level.</span>
</li>
<li id="cite_note-29"><span class="mw-cite-backlink"><b><a href="#cite_ref-29">^</a></b></span> <span class="reference-text"><i>Scheduling</i> based on importance is not the same as greedy <i>dispatching</i> based on importance.</span>
</li>
<li id="cite_note-34"><span class="mw-cite-backlink"><b><a href="#cite_ref-34">^</a></b></span> <span class="reference-text">This is more general than Locke's introduction of the term <i>critical time</i> in Locke 86.</span>
</li>
<li id="cite_note-35"><span class="mw-cite-backlink"><b><a href="#cite_ref-35">^</a></b></span> <span class="reference-text">There is a discontinuity in either the function or its first or second derivative.</span>
</li>
<li id="cite_note-37"><span class="mw-cite-backlink"><b><a href="#cite_ref-37">^</a></b></span> <span class="reference-text">For example, mathematical evidence theories such as <a href="Dempster-Shafer_Theory" class="mw-redirect" title="Dempster-Shafer Theory">Dempster-Shafer Theory</a>, <a href="Imprecise_probability" title="Imprecise probability">imprecise probability</a> theories, etc. may be used for certain system models having epistemic uncertainties.</span>
</li>
<li id="cite_note-38"><span class="mw-cite-backlink"><b><a href="#cite_ref-38">^</a></b></span> <span class="reference-text"><i>Operating</i> is used as the general case to include non-computational (e.g., mechatronic) actions as well as computational tasks that execute.</span>
</li>
<li id="cite_note-43"><span class="mw-cite-backlink"><b><a href="#cite_ref-43">^</a></b></span> <span class="reference-text">Time-dependent scheduling (i.e., some actions' operation durations are functions of their starting times) is distinct from, and not limited to, real-time scheduling in the sense of actions having deadlines (or critical times).</span>
</li>
<li id="cite_note-44"><span class="mw-cite-backlink"><b><a href="#cite_ref-44">^</a></b></span> <span class="reference-text"><i>Sequentially exclusive</i> is a special case of shared access, used here for simplicity without loss of generality.</span>
</li>
<li id="cite_note-45"><span class="mw-cite-backlink"><b><a href="#cite_ref-45">^</a></b></span> <span class="reference-text">Some UA schedulers may remove an overload in a greedy manner—cf. §7.5.1 in Locke 86.</span>
</li>
</ol></div></div>
<div class="mw-heading mw-heading2"><h2 id="References">References</h2></div>
<div class="reflist">
<div class="mw-references-wrap mw-references-columns"><ol class="references">
<li id="cite_note-Jensen+_85-1"><span class="mw-cite-backlink"><b><a href="#cite_ref-Jensen+_85_1-0">^</a></b></span> <span class="reference-text">E. Douglas Jensen, C. Douglas Locke, and Hideyuki Tokuda. <i>A Time-Value Driven Scheduling Model for Real-Time Operating Systems,</i> Proc. Symposium on Real-Time Systems, IEEE, 1985.</span>
</li>
<li id="cite_note-Jensen_93-2"><span class="mw-cite-backlink">^ <a href="#cite_ref-Jensen_93_2-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Jensen_93_2-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Jensen_93_2-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text">E. Douglas Jensen. <i>A Timeliness Model for Asynchronous Decentralized Computer Systems,</i> Proc. International Symposium on Autonomous Decentralized Systems, IEEE, 1993</span>
</li>
<li id="cite_note-Jensen_77-4"><span class="mw-cite-backlink"><b><a href="#cite_ref-Jensen_77_4-0">^</a></b></span> <span class="reference-text">E. Douglas Jensen. Chapter 3 <i>Radar Scheduling,</i> Section 1 <i>The Scheduling Problem</i> in Gouda+ 77 (unclassified version).</span>
</li>
<li id="cite_note-Gouda+_77-5"><span class="mw-cite-backlink"><b><a href="#cite_ref-Gouda+_77_5-0">^</a></b></span> <span class="reference-text">Mohamed G. Gouda, Yi-Wu Han, E. Douglas Jensen, Wesley D. Johnson, Richard Y. Kain (Editor). <i>Distributed Data Processing Technology, Vol. IV, Applications of DDP Technology to BMD: Architectures and Algorithms,</i> unclassified version, Defense Technical Information Center a047477, Honeywell Systems and Research Center, Minneapolis, MN, 1977.</span>
</li>
<li id="cite_note-Maynard+_88_&amp;_08-6"><span class="mw-cite-backlink">^ <a href="#cite_ref-Maynard+_88_&amp;_08_6-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Maynard+_88_&amp;_08_6-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Maynard+_88_&amp;_08_6-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text">David P. Maynard, Samuel E. Shipman, Raymond K. Clark, J. Duane Northcutt, E. Douglas Jensen, Russell B. Kegley, Betsy A. Zimmerman, Peter J. Keleher. <i>An Example Real-Time Battle Management Command and Control Application for Alpha,</i> Section 8.2.1, Archons Project Technical Report, 1988, and public version 2008.</span>
</li>
<li id="cite_note-Ravindran+_05-7"><span class="mw-cite-backlink">^ <a href="#cite_ref-Ravindran+_05_7-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Ravindran+_05_7-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Binoy Ravindran, E. Douglas Jensen, and Peng Li. <i>On Recent Advances in Time/Utility Function Real-Time Scheduling and Resource Management,</i> Proc. Eighth IEEE International Symposium on Object-Oriented Real-Time Distributed Computing, 2005.</span>
</li>
<li id="cite_note-Aldami+_99-8"><span class="mw-cite-backlink"><b><a href="#cite_ref-Aldami+_99_8-0">^</a></b></span> <span class="reference-text">Saud A. Aldami and Alan Burns. <i>Dynamic Value-Density for Scheduling Real-Time Systems,</i> Proc. 11th Euromicro Conference on Real-Time Systems, IEEE, 1999.</span>
</li>
<li id="cite_note-Burns+_00-9"><span class="mw-cite-backlink">^ <a href="#cite_ref-Burns+_00_9-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Burns+_00_9-1"><sup><i><b>b</b></i></sup></a> <a href="#cite_ref-Burns+_00_9-2"><sup><i><b>c</b></i></sup></a></span> <span class="reference-text">Alan Burns, D. Prasad, A. Bondavalli, F. Di Giandomenico, K. Ramamritham, J. Stankovic, L. Strigini. <i>The meaning and role of value in scheduling flexible real-time systems,</i> Journal of Systems Architecture, Elsivier, 2000.</span>
</li>
<li id="cite_note-Prasad+_03-10"><span class="mw-cite-backlink"><b><a href="#cite_ref-Prasad+_03_10-0">^</a></b></span> <span class="reference-text">Divya Prasad, Alan Burns, and Martin Atkins. <i>The Valid Use of Utility in Adaptive Real-Time Systems.</i> Real-Time Systems, Kluwer, 2003.</span>
</li>
<li id="cite_note-Chen+_96-11"><span class="mw-cite-backlink">^ <a href="#cite_ref-Chen+_96_11-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Chen+_96_11-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Ken Chen and Paul Muhlethaler. <i>A Family of Scheduling Algorithms for Real-Time Systems Using Time Value Functions.</i> Real-Time Systems, vol. 10 no. 3, Kluwer, 1996.</span>
</li>
<li id="cite_note-Tidwell+_10-12"><span class="mw-cite-backlink"><b><a href="#cite_ref-Tidwell+_10_12-0">^</a></b></span> <span class="reference-text">Terry Tidwell, Robert Glaubius, Christopher D. Gill and William D. Smart. <i>Optimizing Expected Time Utility in Cyber-Physical Systems Schedulers,</i> Proc. IEEE Real-Time Systems Symposium, 2010.</span>
</li>
<li id="cite_note-Ronén+_99-13"><span class="mw-cite-backlink"><b><a href="#cite_ref-Ronén+_99_13-0">^</a></b></span> <span class="reference-text">Yagil Ronén, Daniel Mossé, and Martha E. Pollack. <i>Value-Density Algorithms for the Deliberation-Scheduling Problem,</i> ACM SIGART Bulletin, Volume 7 Issue 2, 1996.</span>
</li>
<li id="cite_note-Barcís_20-14"><span class="mw-cite-backlink"><b><a href="#cite_ref-Barcís_20_14-0">^</a></b></span> <span class="reference-text">Michał Barcís, Agata Barcís, and Hermann Hellwagner. <i>An Evaluation Model for Information Distribution in Multi-Robot Systems,</i> Sensors, January 2020.</span>
</li>
<li id="cite_note-Shireen_Seakhoa-King+_19-15"><span class="mw-cite-backlink"><b><a href="#cite_ref-Shireen_Seakhoa-King+_19_15-0">^</a></b></span> <span class="reference-text">Shireen Seakhoa-King, Paul Balaji, Nicolas Trama Alvarez, and William J. Knottenbelt. <i>Revenue-Driven Scheduling in Drone Delivery Networks with Time-Sensitive Service Level Agreements,</i> Proc. 12th EAI International Conference on Performance Evaluation Methodologies and Tools, ACM, 2019.</span>
</li>
<li id="cite_note-Baums_12-16"><span class="mw-cite-backlink"><b><a href="#cite_ref-Baums_12_16-0">^</a></b></span> <span class="reference-text">Aldis Baums. <i>Automatic Control and Computer Sciences,</i> Vol. 46, No. 6, Allerton Press, 2012.</span>
</li>
<li id="cite_note-Ibarz+_20-17"><span class="mw-cite-backlink"><b><a href="#cite_ref-Ibarz+_20_17-0">^</a></b></span> <span class="reference-text">Jean Ibarz, Michaël Lauer, Matthieu Roy, Jean-Charles Fabre, Olivier Flébus. <i>Optimizing Vehicle-to-Cloud Data Transfers using Soft Real-Time Scheduling Concepts</i>, Proc. 28th International Conference on Real-Time Networks and Systems, ACM, 2020.</span>
</li>
<li id="cite_note-Habets_19-18"><span class="mw-cite-backlink"><b><a href="#cite_ref-Habets_19_18-0">^</a></b></span> <span class="reference-text">Rutger Habets. <i>Improving the line performance of packaging line 41 at Heineken Zoeterwoude,</i> Bachelor of Science project thesis, Industrial Engineering and Management, University of Twente, 2019.</span>
</li>
<li id="cite_note-Haritsa+_93-19"><span class="mw-cite-backlink"><b><a href="#cite_ref-Haritsa+_93_19-0">^</a></b></span> <span class="reference-text">Jayant R. Haritsa, Jayant R., Michael J. Carey, and Miron Livney. <i>Value-Based Scheduling in Real-Time Databases,</i> VLDB Journal, 2 (2) 1993.</span>
</li>
<li id="cite_note-Briceño+_11-20"><span class="mw-cite-backlink"><b><a href="#cite_ref-Briceño+_11_20-0">^</a></b></span> <span class="reference-text">Luis Diego Briceño, Bhavesh Khemka, Howard Jay Siegel, Anthony A. Maciejewski, Christopher Groër, Gregory Koenig, Gene Okonski, and Steve Poole. <i>Time Utility Functions for Modeling and Evaluating Resource Allocations in a Heterogeneous Computing System,</i> Proc. IEEE International Symposium on Parallel and Distributed Processing, 2011.</span>
</li>
<li id="cite_note-Tunc+_16-21"><span class="mw-cite-backlink"><b><a href="#cite_ref-Tunc+_16_21-0">^</a></b></span> <span class="reference-text">Cihan Tunc, Nirmal Kumbhare, Ali Akoglu, Salim Hariri, Dylan Machovec, Howard Jay Siegel. <i>Value of Service Based Task Scheduling for Cloud Computing Systems,</i> Proc. International Conference on Cloud and Autonomic Computing, 2016.</span>
</li>
<li id="cite_note-Ravi+_12-22"><span class="mw-cite-backlink"><b><a href="#cite_ref-Ravi+_12_22-0">^</a></b></span> <span class="reference-text">Vignesh T. Ravi1, Michela Becchi2, Gagan Agrawal1, and Srimat Chakradhar. <i>ValuePack: Value-Based Scheduling Framework for CPU-GPU Clusters,</i> Proc. IEEE International Conference on High Performance Computing, Networking, Storage and Analysis, 2012.</span>
</li>
<li id="cite_note-Young+_06-23"><span class="mw-cite-backlink"><b><a href="#cite_ref-Young+_06_23-0">^</a></b></span> <span class="reference-text">Alvin AuYoung, Laura Grit, Janet Wiener, John Wilkes. <i>Service contracts and aggregate utility functions,</i> Proc. 15th IEEE International Symposium on High Performance Distributed Computing, 2006.</span>
</li>
<li id="cite_note-Wang+_04-24"><span class="mw-cite-backlink"><b><a href="#cite_ref-Wang+_04_24-0">^</a></b></span> <span class="reference-text">Jinggang Wang and Binoy Ravindran. <i>Time-Utility Function-Driven Switched Ethernet: Packet Scheduling Algorithm, Implementation, and Feasibility Analysis,</i> IEEE Transactions on Parallel and Distributed Systems, vol. 15, no. 2, February 2004.</span>
</li>
<li id="cite_note-Cho+_09-25"><span class="mw-cite-backlink"><b><a href="#cite_ref-Cho+_09_25-0">^</a></b></span> <span class="reference-text">Hyeonjoong Cho, Binoy Ravindran, Chewoo Na. <i>Garbage Collector Scheduling in Dynamic, Multiprocessor Real-Time Systems,</i> IEEE Transactions on Parallel and Distributed Systems 20(6), June 2009.</span>
</li>
<li id="cite_note-Feizabadi+_07-26"><span class="mw-cite-backlink"><b><a href="#cite_ref-Feizabadi+_07_26-0">^</a></b></span> <span class="reference-text">Shahrooz Feizabadi and Godmar Back. <i>Garbage collection-aware utility accrual scheduling,</i> Real-Time Systems Journal, July 2007, Volume 36, Issue 1–2, 2007.</span>
</li>
<li id="cite_note-Clark_90-27"><span class="mw-cite-backlink"><b><a href="#cite_ref-Clark_90_27-0">^</a></b></span> <span class="reference-text">Raymond K. Clark. <i>Scheduling Dependent Real-Time Activities,</i> Ph.D. Dissertation, CMU-CS-90-155, Computer Science Department, Carnegie Mellon Univ., 1990.</span>
</li>
<li id="cite_note-Clark+_99-28"><span class="mw-cite-backlink">^ <a href="#cite_ref-Clark+_99_28-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Clark+_99_28-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Raymond K. Clark, E. Douglas Jensen, Arkady Kanevsky, John Maurer, Paul Wallace, Tom Wheeler, Yun Zhang, Douglas M. Wells, Tom Lawrence, and Pat Hurley. <i>An Adaptive, Distributed Airborne Tracking System,</i> IEEE Parallel and Distributed Real-Time Systems, volume 1586 of LNCS, Springer-Verlag, 1999.</span>
</li>
<li id="cite_note-Locke_86-30"><span class="mw-cite-backlink"><b><a href="#cite_ref-Locke_86_30-0">^</a></b></span> <span class="reference-text">C. Douglas Locke. <i>Best-Effort Decision Making for Real-Time Scheduling,</i> Ph.D. Thesis CMU-CS-86-134, Computer Science Department, Carnegie-Mellon University, 1986.</span>
</li>
<li id="cite_note-Li_04-31"><span class="mw-cite-backlink"><b><a href="#cite_ref-Li_04_31-0">^</a></b></span> <span class="reference-text">Peng Li. <i>Utility Accrual Real-Time Scheduling: Models and Algorithms,</i> Ph.D. dissertation, Virginia Polytechnic Institute and State University, 2004.</span>
</li>
<li id="cite_note-Li+_06-32"><span class="mw-cite-backlink"><b><a href="#cite_ref-Li+_06_32-0">^</a></b></span> <span class="reference-text">Peng Li, Haisang Wu, Binoy Ravindran, and E. Douglas Jensen. <i>A Utility Accrual Scheduling Algorithm for Real-Time Activities with Mutual Exclusion Resource Constraints,</i> IEEE Transactions on Computers, vol. 55, no. 4, April 2006.</span>
</li>
<li id="cite_note-Guo+_16-33"><span class="mw-cite-backlink"><b><a href="#cite_ref-Guo+_16_33-0">^</a></b></span> <span class="reference-text">Zhishan Guo and Sanjoy Buruah. <i>A Neurodynamic Approach for Real-Time Scheduling via Maximizing Piecewise Linear Utility</i>, IEEE Transactions on Neural Networks and Learning Systems, vol. 27 no. 2, February 2016.</span>
</li>
<li id="cite_note-Erikson_14-36"><span class="mw-cite-backlink"><b><a href="#cite_ref-Erikson_14_36-0">^</a></b></span> <span class="reference-text">Jeremy P. Erickson. <i>Managing Tardiness Bounds and Overload in Soft Real-Time Systems</i>, Ph.D. dissertation, University of North Carolina, 2014.</span>
</li>
<li id="cite_note-Gawiejnowicz_20a-39"><span class="mw-cite-backlink">^ <a href="#cite_ref-Gawiejnowicz_20a_39-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Gawiejnowicz_20a_39-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Stanislaw Gawiejnowicz. <i>A review of four decades of time-dependent scheduling: main results, new topics, and open problems,</i> Journal of Scheduling 23, 3–47, Springer, 2020.</span>
</li>
<li id="cite_note-Glazebrook_92-40"><span class="mw-cite-backlink">^ <a href="#cite_ref-Glazebrook_92_40-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Glazebrook_92_40-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">K. D. Glazebrook. <i>Single-machine scheduling of stochastic jobs subject to deterioration or delay,</i> Naval Research Logistics 39, no. 5, Wiley, 1992.</span>
</li>
<li id="cite_note-Balli+_07-41"><span class="mw-cite-backlink">^ <a href="#cite_ref-Balli+_07_41-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Balli+_07_41-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Umut Balli, Haisang Wu, Binoy Ravindran, Jonathan Stephen Anderson, E. Douglas Jensen. <i>Utility Accrual Real-Time Scheduling under Variable Cost Functions,</i> IEEE Transactions on Computers, Volume 56, Number 3, March 2007.</span>
</li>
<li id="cite_note-Ho+_93-42"><span class="mw-cite-backlink">^ <a href="#cite_ref-Ho+_93_42-0"><sup><i><b>a</b></i></sup></a> <a href="#cite_ref-Ho+_93_42-1"><sup><i><b>b</b></i></sup></a></span> <span class="reference-text">Kevin I-J. Ho, Joseph Y-T. Leung and W-D. Wei. <i>Complexity of scheduling tasks with time-dependent execution times,</i> Information Processing Letters 48 (1993), no. 6, Elsevier, 20 December 1993.</span>
</li>
</ol></div></div>
<div class="mw-heading mw-heading2"><h2 id="External_links">External links</h2></div>
<ul><li><a rel="nofollow" class="external text" href="https://www.real-time.org">Real-Time for the Real World.</a></li>
<li><a rel="nofollow" class="external text" href="https://www.ssrg.ece.vt.edu/allpapers.php">2006-2009, Systems Software Research Group, Binoy Ravindran, ECE, Virginia Tech.</a></li>
<li><a rel="nofollow" class="external text" href="https://www.stern.nyu.edu/om/faculty/pinedo/schedtheory/book5/index.html">Michael L. Pindo, <i>Scheduling: Theory, Algorithms, and Systems,</i> 5th ed., 2015.</a></li>
<li><a rel="nofollow" class="external text" href="https://www.springer.com/us/book/9783662593615?gclid=Cj0KCQjwsuP5BRCoARIsAPtX_wHOG2nAkt8eTSFJbhNa4VXlQBt_xhirlmE-ECUV5cnq8nPqgH6gpJUaAuGaEALw_wcB">Stanislaw Gawiejnowicz, <i>Models and Algorithms of Time-Dependent Scheduling</i></a>, 2nd ed., eBook <style data-mw-deduplicate="TemplateStyles:r1238218222">
/* start https://en.wikipedia.org/ */


.mw-parser-output cite.citation{font-style:inherit;word-wrap:break-word}.mw-parser-output .citation q{quotes:"\"""\"""'""'"}.mw-parser-output .citation:target{background-color:rgba(0,127,255,0.133)}.mw-parser-output .id-lock-free.id-lock-free a{background:url("./mw/Lock-green.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-limited.id-lock-limited a,.mw-parser-output .id-lock-registration.id-lock-registration a{background:url("./mw/Lock-gray-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .id-lock-subscription.id-lock-subscription a{background:url("./mw/Lock-red-alt-2.svg")right 0.1em center/9px no-repeat}.mw-parser-output .cs1-ws-icon a{background:url("./mw/Wikisource-logo.svg")right 0.1em center/12px no-repeat}body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-free a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-limited a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-registration a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .id-lock-subscription a,body:not(.skin-timeless):not(.skin-minerva) .mw-parser-output .cs1-ws-icon a{background-size:contain;padding:0 1em 0 0}.mw-parser-output .cs1-code{color:inherit;background:inherit;border:none;padding:inherit}.mw-parser-output .cs1-hidden-error{display:none;color:var(--color-error,#d33)}.mw-parser-output .cs1-visible-error{color:var(--color-error,#d33)}.mw-parser-output .cs1-maint{display:none;color:#085;margin-left:0.3em}.mw-parser-output .cs1-kern-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right{padding-right:0.2em}.mw-parser-output .citation .mw-selflink{font-weight:inherit}@media screen{.mw-parser-output .cs1-format{font-size:95%}html.skin-theme-clientpref-night .mw-parser-output .cs1-maint{color:#18911f}}@media screen and (prefers-color-scheme:dark){html.skin-theme-clientpref-os .mw-parser-output .cs1-maint{color:#18911f}}


/* end https://en.wikipedia.org/ */
</style><a href="ISBN_(identifier)" class="mw-redirect" title="ISBN (identifier)">ISBN</a>&nbsp;<bdi>978-3-662-59362-2</bdi>, Springer, 2020.</li>
<li><a rel="nofollow" class="external text" href="https://www.academia.edu/15210217/Fifty_years_of_scheduling_a_survey_of_milestones?auto=download&amp;email_work_card=download-paper">Chris N. Potts and Vitaly A. Strusevich, <i>Fifty Years of Scheduling: A Survey of Milestones</i> (2009)</a></li>
<li><a rel="nofollow" class="external text" href="https://www.springer.com/journal/10951">Journal of scheduling.</a></li>
<li><a rel="nofollow" class="external text" href="http://www.schedulingconference.org/">Multidisciplinary International Conference on Scheduling.</a></li>
<li><a rel="nofollow" class="external text" href="https://www.researchgate.net/project/The-Third-International-Workshop-on-Dynamic-Scheduling-Problems-IWDSP-2020">International Workshop on Dynamic Scheduling Problems.</a></li></ul></div><!--htdig_noindex--><div><div class="zim-footer">
This article is issued from <a class="external text" title="Last edited on 2025-03-19" href="https://en.wikipedia.org/wiki/?title=Time-utility_function&amp;oldid=1281227479">Wikipedia</a>. The text is available under <a class="external text" href="https://creativecommons.org/licenses/by-sa/4.0/deed.en">Creative Commons Attribution-Share Alike 4.0</a> unless otherwise noted. Additional terms may apply for the media files.
</div>
</div><!--/htdig_noindex--></div>
</div>
</main>
</div>
</div>
</div>

</body></html>